Method and system for transaction authorization via controlled blockchain

ABSTRACT

A method for processing an electronic payment transaction includes: storing an account profile including a plurality of account numbers; receiving a first authorization request for a payment transaction that includes a first account number of the plurality of account numbers, a first time, and a first location; processing the first payment transaction; receiving a second authorization request for a different transaction including a second primary account number of the plurality of account numbers, a second time, and a second location, where the second account number is associated with a different issuer than the first account number; determining a likelihood of fraud based on the first time and location and the second time and location; and forwarding the second authorization request to the different issuer if the likelihood of fraud is below a threshold, or transmitting an authorization response indicating decline if the likelihood of fraud is above the threshold.

FIELD

The present disclosure relates to the processing of electronic paymenttransactions, specifically the use of an authorization for a paymenttransaction funded by a transaction account issued by a first issuer inthe authorization of a second payment transaction funded by a differenttransaction account issued by a second issuer, where the transactionaccounts are associated through biographical information.

BACKGROUND

Generally, electronic payment transactions are processed using a systemwhere an issuing institution that issued a transaction account used tofund the transaction will approve or decline the transaction. In manycases, the determination to approve or decline the transaction is madebased on, among other criteria, transaction history of that transactionaccount. For instance, if a consumer wants to make a purchase at thesame merchant and the same time and day of the week as the consumer hasmade several times prior using the same transaction account, the issuinginstitution may be more likely to approve the transaction having theimpression that it is the genuine consumer. Similarly, if a transactionis conducted in one country and then a second transaction attempted ashort time after in a different country a significant distance away, theissuing institution may likely decline the transaction due to fraudconcerns.

Such considerations can be useful in the approval and denial ofelectronic payment transactions. However, these kinds of considerationsare only as useful as the data available to the issuing institutions. Incases where a consumer may have multiple transaction accounts that areused to fund electronic payment transactions, the transaction historyavailable to any single issuer may be incomplete and thus ineffectivefor determining approval or denial based thereon. In addition, intraditional systems, it may be impossible due to privacy regulations andrestrictions for one issuing institution to obtain transactionalinformation for a consumer from a different issuing institution.Furthermore, due to inexperience handling such data, issuinginstitutions may be inefficient, if not incapable, of taking such datainto account when determining approval and denial of paymenttransactions. That is, a business need creates a technical challenge toachieve the desired effect that avoids the technical problems identifiedabove for instance.

Thus, there is a need for a technological system that is configured toidentify, while maintaining consumer security and privacy, transactionalhistory for a consumer across multiple issuing institutions for usethereof in determining approval or denial of an attempted electronicpayment transaction.

SUMMARY

The present disclosure provides a description of systems and methods forprocessing an electronic payment transaction. A processing systemidentifies transaction accounts issued to the same consumer fromdifferent issuing institutions via the use of biographical data.Transactions are tracked across the issuing institution such that, whena new authorization request is received, the past transaction history,independent of issuing institution, is taken into account. Theprocessing system is configured to decline transactions on behalf of theissuing institutions if the transactional history is such that fraud isdetected, resulting in a more efficient processing system where fraudcan be prevented in instances where the issuing institution would havebeen unable to detect such fraud, and in a manner that reduces networkcommunications and processing time expended by issuing institutions.

A method for processing an electronic payment transaction includes:storing, in an account database of a processing server, an accountprofile, wherein the account profile includes at least a plurality ofprimary account numbers and one or more biographical data values, whereeach of the plurality of primary account numbers is associated with atransaction account and the one or more biographical data values areassociated with each of the transaction accounts related to theplurality of primary account numbers; receiving, by a receiving deviceof the processing server, a first authorization request for a firstpayment transaction, wherein the first authorization request isformatted according to one or more standards and includes a plurality ofdata elements configured to store transaction data including at least afirst primary account number of the plurality of primary accountnumbers, a first transaction time, and a first geographic location;processing, by the processing server, the first payment transaction;receiving, by the receiving device of the processing server, a secondauthorization request for a second payment transaction from an externalsystem, wherein the second authorization request is formatted accordingto the one or more standards and includes a plurality of data elementsconfigured to store transaction data including at least a second primaryaccount number of the plurality of primary account numbers, a secondtransaction time, and a second geographic location, where the secondprimary account number is associated with a transaction account issuedby a different issuer than a transaction account associated with thefirst primary account number; determining, by the processing server, alikelihood of fraud based on at least the first transaction time andfirst geographic location stored in the first authorization request andthe second transaction time and second geographic location stored in thesecond authorization request; and forwarding, by a transmitting deviceof the processing server, the second authorization request to thedifferent issuer if the determined likelihood of fraud is below apredetermined threshold, or transmitting, by the transmitting device ofthe processing server, an authorization response for the second paymenttransaction to the external system indicating decline of the secondpayment transaction if the determined likelihood of fraud is above thepredetermined threshold.

A system for processing an electronic payment transaction includes: anaccount database of a processing server configured to store an accountprofile, wherein the account profile includes at least a plurality ofprimary account numbers and one or more biographical data values, whereeach of the plurality of primary account numbers is associated with atransaction account and the one or more biographical data values areassociated with each of the transaction accounts related to theplurality of primary account numbers; a receiving device of theprocessing server configured to receive a first authorization requestfor a first payment transaction, wherein the first authorization requestis formatted according to one or more standards and includes a pluralityof data elements configured to store transaction data including at leasta first primary account number of the plurality of primary accountnumbers, a first transaction time, and a first geographic location; atransmitting device of the processing server; and the processing serverconfigured to process the first payment transaction, wherein thereceiving device of the processing server is further configured toreceive a second authorization request for a second payment transactionfrom an external system, wherein the second authorization request isformatted according to the one or more standards and includes aplurality of data elements configured to store transaction dataincluding at least a second primary account number of the plurality ofprimary account numbers, a second transaction time, and a secondgeographic location, where the second primary account number isassociated with a transaction account issued by a different issuer thana transaction account associated with the first primary account number,the processing server is further configured to determine a likelihood offraud based on at least the first transaction time and first geographiclocation stored in the first authorization request and the secondtransaction time and second geographic location stored in the secondauthorization request, and the transmitting device of the processingserver is configured to transmit the second authorization request to thedifferent issuer if the determined likelihood of fraud is below apredetermined threshold, or transmit an authorization response for thesecond payment transaction to the external system indicating decline ofthe second payment transaction if the determined likelihood of fraud isabove the predetermined threshold.

BRIEF DESCRIPTION OF THE DRAWING FIGURES

The scope of the present disclosure is best understood from thefollowing detailed description of exemplary embodiments when read inconjunction with the accompanying drawings. Included in the drawings arethe following figures:

FIG. 1 is a block diagram illustrating a high level system architecturefor processing electronic payment transactions in accordance withexemplary embodiments.

FIG. 2 is a block diagram illustrating the processing server of thesystem of FIG. 1 for the processing of electronic payment transactionsin accordance with exemplary embodiments.

FIG. 3 is a flow diagram illustrating a process for processingelectronic payment transactions by the processing server of FIG. 2 inaccordance with exemplary embodiments.

FIG. 4 is a flow chart illustrating an exemplary method for processingan electronic payment transaction in accordance with exemplaryembodiments.

FIG. 5 is a block diagram illustrating a computer system architecture inaccordance with exemplary embodiments.

Further areas of applicability of the present disclosure will becomeapparent from the detailed description provided hereinafter. It shouldbe understood that the detailed description of exemplary embodiments areintended for illustration purposes only and are, therefore, not intendedto necessarily limit the scope of the disclosure.

DETAILED DESCRIPTION Glossary of Terms

Payment Network—A system or network used for the transfer of money viathe use of cash-substitutes for thousands, millions, and even billionsof transactions during a given period. Payment networks may use avariety of different protocols and procedures in order to process thetransfer of money for various types of transactions. Transactions thatmay be performed via a payment network may include product or servicepurchases, credit purchases, debit transactions, fund transfers, accountwithdrawals, etc. Payment networks may be configured to performtransactions via cash-substitutes, which may include payment cards,letters of credit, checks, transaction accounts, etc. Examples ofnetworks or systems configured to perform as payment networks includethose operated by MasterCard®, VISA®, Discover®, American Express®,PayPal®, etc. Use of the term “payment network” herein may refer to boththe payment network as an entity, and the physical payment network, suchas the equipment, hardware, and software comprising the payment network.

Payment Rails—Infrastructure associated with a payment network used inthe processing of payment transactions and the communication oftransaction messages and other similar data between the payment networkand other entities interconnected with the payment network that handlesthousands, millions, and even billions of transactions during a givenperiod. The payment rails may be comprised of the hardware used toestablish the payment network and the interconnections between thepayment network and other associated entities, such as financialinstitutions, gateway processors, etc. In some instances, payment railsmay also be affected by software, such as via special programming of thecommunication hardware and devices that comprise the payment rails. Forexample, the payment rails may include specifically configured computingdevices that are specially configured for the routing of transactionmessages, which may be specially formatted data messages that areelectronically transmitted via the payment rails, as discussed in moredetail below.

Transaction Account—A financial account that may be used to fund atransaction, such as a checking account, savings account, creditaccount, virtual payment account, etc. A transaction account may beassociated with a consumer, which may be any suitable type of entityassociated with a payment account, which may include a person, family,company, corporation, governmental entity, etc. In some instances, atransaction account may be virtual, such as those accounts operated byPayPal®, etc.

Merchant—An entity that provides products (e.g., goods and/or services)for purchase by another entity, such as a consumer or another merchant.A merchant may be a consumer, a retailer, a wholesaler, a manufacturer,or any other type of entity that may provide products for purchase aswill be apparent to persons having skill in the relevant art. In someinstances, a merchant may have special knowledge in the goods and/orservices provided for purchase. In other instances, a merchant may nothave or require any special knowledge in offered products. In someembodiments, an entity involved in a single transaction may beconsidered a merchant. In some instances, as used herein, the term“merchant” may refer to an apparatus or device of a merchant entity.

Issuer—An entity that establishes (e.g., opens) a letter or line ofcredit in favor of a beneficiary, and honors drafts drawn by thebeneficiary against the amount specified in the letter or line ofcredit. In many instances, the issuer may be a bank or other financialinstitution authorized to open lines of credit. In some instances, anyentity that may extend a line of credit to a beneficiary may beconsidered an issuer. The line of credit opened by the issuer may berepresented in the form of a payment account, and may be drawn on by thebeneficiary via the use of a payment card. An issuer may also offeradditional types of payment accounts to consumers as will be apparent topersons having skill in the relevant art, such as debit accounts,prepaid accounts, electronic wallet accounts, savings accounts, checkingaccounts, etc., and may provide consumers with physical or non-physicalmeans for accessing and/or utilizing such an account, such as debitcards, prepaid cards, automated teller machine cards, electronicwallets, checks, etc.

Payment Transaction—A transaction between two entities in which money orother financial benefit is exchanged from one entity to the other. Thepayment transaction may be a transfer of funds, for the purchase ofgoods or services, for the repayment of debt, or for any other exchangeof financial benefit as will be apparent to persons having skill in therelevant art. In some instances, payment transaction may refer totransactions funded via a payment card and/or payment account, such ascredit card transactions. Such payment transactions may be processed viaan issuer, payment network, and acquirer. The process for processingsuch a payment transaction may include at least one of authorization,batching, clearing, settlement, and funding. Authorization may includethe furnishing of payment details by the consumer to a merchant, thesubmitting of transaction details (e.g., including the payment details)from the merchant to their acquirer, and the verification of paymentdetails with the issuer of the consumer's payment account used to fundthe transaction. Batching may refer to the storing of an authorizedtransaction in a batch with other authorized transactions fordistribution to an acquirer. Clearing may include the sending of batchedtransactions from the acquirer to a payment network for processing.Settlement may include the debiting of the issuer by the payment networkfor transactions involving beneficiaries of the issuer. In someinstances, the issuer may pay the acquirer via the payment network. Inother instances, the issuer may pay the acquirer directly. Funding mayinclude payment to the merchant from the acquirer for the paymenttransactions that have been cleared and settled. It will be apparent topersons having skill in the relevant art that the order and/orcategorization of the steps discussed above performed as part of paymenttransaction processing.

Blockchain—A public ledger of all transactions of a blockchain-basedcurrency. One or more computing devices may comprise a blockchainnetwork, which may be configured to process and record transactions aspart of a block in the blockchain. Once a block is completed, the blockis added to the blockchain and the transaction record thereby updated.In many instances, the blockchain may be a ledger of transactions inchronological order, or may be presented in any other order that may besuitable for use by the blockchain network. In some configurations,transactions recorded in the blockchain may include a destinationaddress and a currency amount, such that the blockchain records how muchcurrency is attributable to a specific address. In some instances, thetransactions are financial and others not financial, or might includeadditional or different information, such as a source address,timestamp, etc. In some embodiments, a blockchain may also oralternatively include nearly any type of data as a form of transactionthat is or needs to be placed in a distributed database that maintains acontinuously growing list of data records hardened against tampering andrevision, even by its operators, and may be confirmed and validated bythe blockchain network through proof of work and/or any other suitableverification techniques associated therewith. In some cases, dataregarding a given transaction may further include additional data thatis not directly part of the transaction appended to transaction data. Insome instances, the inclusion of such data in a blockchain mayconstitute a transaction. In such instances, a blockchain may not bedirectly associated with a specific digital, virtual, fiat, or othertype of currency.

System for Processing of Electronic Payment Transactions

FIG. 1 illustrates a system 100 for the processing of electronic paymenttransactions where authorization is performed on behalf of an issuinginstitution based on transactional history of a consumer across multipleissuing institutions where, in some cases, blockchain may be used forstorage of the transactional history.

The system 100 may include a processing server 102. The processingserver 102, discussed in more detail below, may be configured toparticipate in the processing of electronic payment transactionsutilizing transactional history for a consumer 104 across a plurality ofdifferent issuing institutions 106, such as the issuing institutions 106a and 106 b illustrated in FIG. 1. In the system 100, a consumer 104 mayhave transaction accounts issued thereto that may be used in the fundingof electronic payment transactions by two or more issuing institutions106. Each issuing institution 106 may issue a transaction account to theconsumer 104 and, for each transaction account, may issue one or morepayment instruments 108 to the consumer 104, such as the paymentinstruments 108 a and 108 b illustrated in FIG. 1. The paymentinstrument 108 may be encoded with or otherwise used to convey paymentcredentials associated with the related transaction account. Paymentcredentials may include, for example, a primary account number and anyother data used in the identification and authentication of atransaction account for use in funding an electronic paymenttransaction, such as a name, expiration date, security code, applicationcryptogram, transaction counter, etc.

The consumer 104 may use the payment instruments 108 at merchant systems110 when conducting electronic payment transactions. The consumer 104may present a payment instrument 108 to a merchant system 110, which mayread or otherwise receive payment credentials from the paymentinstrument. The merchant system 110 may include the payment credentialsin transaction data that is submitted to a payment network 112 forprocessing of the payment transaction. In some embodiments, the merchantsystem 110 may submit the transaction data directly to the paymentnetwork 112 via payment rails associated therewith. In otherembodiments, the merchant system 110 may transmit the transaction datato an intermediate entity, such as an acquiring institution or gatewayprocessor, which may submit the transaction data to the payment network112 via payment rails associated therewith.

As part of the processing of the payment transaction, the paymentnetwork 112 may receive an authorization request for the paymenttransaction. An authorization request may be a type of transactionmessage indicating that authorization is requested for a related paymenttransaction. A transaction message may be a specially formatted datamessage that is formatted according to one or more standards governingthe interchange of financial transactional messages, such as theInternational Organization of Standardization's ISO 8583 or ISO 20022standards. A transaction message may include a message type indicatorindicating a type of the message (e.g., an authorization request,authorization response, etc.) as well as a plurality of data elements,where each data element is configured to store data for the electronicpayment transaction. In some cases, the standards and/or one or morebitmaps included in the transaction message may be used to indicate whatdata elements store what transactional data. Data elements may beconfigured, for example, to store the primary account number, otherpayment credentials, a transaction amount, transaction time, transactiondate, geographic location, currency type, merchant identificationnumber, acquirer data, issuer data, product data, offer data, rewarddata, loyalty data, etc. In some cases, the merchant system 110 maygenerate the authorization request for the electronic paymenttransaction. In other cases, an intermediate entity (e.g., acquiringinstitution, gateway processor, etc.) may receive the transaction datafrom the merchant system 110 and generate the authorization requestbased thereon.

In a traditional system, the payment network 112 would forward theauthorization request to the issuing institution 106 that issued thetransaction account used by the consumer 104 to fund the electronicpayment transaction, where the issuing institution 106 would approve ordeny the payment transaction and electronically transmit anauthorization response (e.g., a transaction message with a message typeindicator indicating an authorization response) back to the paymentnetwork 112. In the system 100, the processing server 102 may receivethe authorization request (e.g., directly from the payment network 112or from the issuing institution 106 after forwarding of theauthorization request by the payment network 112) to perform on-behalfprocessing for the issuing institution 106. The processing server 102may determine if the transaction should be declined, or if the issuinginstitution 106 should be contacted for further approval based on pasttransaction history of the consumer 104 involved in the paymenttransaction, as discussed in more detail below.

The processing server 102 may be configured to take past authorizationrequests into account when processing a newly received authorizationrequest for a consumer 104, wherein the past authorization requests maybe associated with different issuing institutions 106 (e.g., asindicated via the included primary account numbers). When anauthorization request is received by the processing server 102, theauthorization request or data included therein may be stored in aprofile associated with the consumer 104, discussed in more detailbelow. The processing server 102 may continue to store authorizationrequests, or data included therein, for any payment transactions thatcan be attributed to the consumer 104 regardless of the issuinginstitution 106. A payment transaction may be attributed to the consumer104 based on biographical data associated with the transaction accountused to fund the payment transaction.

The processing server 102 may be configured to receive biographicalinformation for transaction accounts from associated issuinginstitutions 106. Biographical information may include any informationmade available by an issuing institution 106 regarding an authorizeduser of a transaction account. Such information may include, forexample, a name, phone number, e-mail address, computing deviceidentifier, username, social security number, etc. In some cases, eachconsumer 104 may first provide their consent to the issuing institution106 for such data to be made available to the processing server 102. Insome instances, the biographical information may be anonymized prior totransmission to the processing server 102, or may be anonymized by theprocessing server 102 upon receipt. For example, a name of the consumer104 may be provided by the issuing institution 106 as the biographicalinformation for a transaction account, but where the name is hashed suchthat the consumer's real name is unknown to the processing server 102and cannot be identified by the processing server 102.

The processing server 102 may receive biographical information fortransaction accounts from multiple issuing institutions 106, where theprocessing server 102 may identify transaction accounts across multipleissuing institutions 106 that are each issued to the consumer 104 orwhere the consumer 104 is otherwise an authorized user of thetransaction account based on the biographical information. For instance,the processing server 102 may receive hashes of names for eachtransaction account, and may match a transaction account from issuinginstitution 106 a with a transaction account from issuing institution106 b to the consumer 104 because of matching name hashes. Eachtransaction account that is matched to a consumer 104 may haveidentifying information thereof (e.g., the primary account number)stored in the consumer's profile.

When a new authorization request is received from the payment network112 (e.g., or an issuing institution 106, as applicable), the processingserver 102 may identify a profile for the consumer 104 involved in therelated electronic payment transaction using the primary account numberor other identifying information found in the authorization request. Theprocessing server 102 may then determine a likelihood of fraud for theattempted payment transaction based on data included in the newauthorization request and data included in one or more priorauthorization requests as found in the profile. For instance, in anexemplary embodiment, the processing server 102 may compare a time andgeographic location in one or more recent authorization requests with atime and geographic location included in the new authorization request.If the times and locations are such that it would be impossible for theconsumer 104 to personally conduct both transactions (e.g., there is onehour between authorization requests but the geographic locations are1,000 miles apart), then the processing server 102 may determine a highlikelihood of fraud. Conversely, if the times and locations are suchthat it is likely the consumer 104 is involved in the new paymenttransaction (e.g., the last two authorizations were for transactions inthe last hour at the same shopping mall as the new authorizationrequest), then a low likelihood of fraud may be determined. Thelikelihood of fraud may be represented by the processing server 102using any suitable method, such as an integer (e.g., on a scale of1-100), name (e.g., very low, low, high, very high), or other value.

The processing server 102 may then determine if the transaction shouldbe declined. The determination may be based on the likelihood of fraud,and may be further based on criteria set forth by the associated issuinginstitution 106. For instance, each issuing institution 106 may have athreshold set for on-behalf declines where the processing server 102 maydecline any attempted payment transaction where the determinedlikelihood of fraud is higher than a predetermined value provided by theissuing institution 106. The processing server 102 may identify such avalue based on the primary account number used in the new authorizationrequest (e.g., where the issuing institution 106 may be identifiedtherefrom, such as based on a bank identification number, issueridentification number, etc.).

If the processing server 102 determines that the attempted paymenttransaction should be declined, then the processing server 102 maygenerate an authorization response for the payment transaction thatincludes a data element configured to store a response code thatindicates that the payment transaction is declined. In some instances,the response code may indicate a decline due to fraud concerns. Theprocessing server 102 may return the authorization response to thepayment network 112, which may proceed with any additional processing asnecessary using traditional methods. The merchant system 110 may beinformed of the transaction decline and may finalize the paymenttransaction accordingly. In an exemplary embodiment, the authorizationrequest, or data included therein, for the declined payment transactionmay be stored in the consumer's profile to be taken into account forfuture determinations.

If the processing server 102 determines that the payment transactionshould not be immediately declined, the processing server 102 mayforward the authorization request to the appropriate issuing institution106. In some cases, the determined likelihood of fraud may be includedin the authorization request (e.g., in a data element reserved forprivate use) or may be transmitted in a data message with theauthorization request or in a separate data message. The issuinginstitution 106 may receive the authorization request and may approve ordeny the transaction using traditional methods. As part of the approvalor denial, an authorization response indicating thereof (e.g., in aresponse code stored in a corresponding data element) may be generatedby the issuing institution 106. In some cases, the authorizationresponse may be transmitted directly to the payment network 112 viapayment rails associated therewith. In other cases, the issuinginstitution 106 may return the authorization response to the processingserver 102, which may forward the authorization response to the paymentnetwork 112. The payment transaction may then be finalized accordinglyby the payment network 112 and merchant system 110.

In some embodiments, a blockchain may be used to store the transactiondata for past payment transactions involving a consumer 104. Theblockchain may be maintained by a blockchain network 114, which may becomprised of a plurality of nodes, where each node may be a computingsystem configured to maintain a copy of the blockchain, generate newblocks, validate blocks generated by other nodes, and perform anyadditional functions associated with operation and use of theblockchain. In some embodiments, the processing server 102 may be a nodein the blockchain network 114.

The blockchain may be a distributed ledger that is comprised of at leasta plurality of blocks. Each block may include at least a block headerand one or more data values. Each block header may include at least atimestamp, a block reference value, and a data reference value. Thetimestamp may be a time at which the block header was generated, and maybe represented using any suitable method (e.g., UNIX timestamp,DateTime, etc.). The block reference value may be a value thatreferences an earlier block (e.g., based on timestamp) in theblockchain. In some embodiments, a block reference value in a blockheader may be a reference to the block header of the most recently addedblock prior to the respective block. In an exemplary embodiment, theblock reference value may be a hash value generated via the hashing ofthe block header of the most recently added block. The data referencevalue may similarly be a reference to the one or more data values storedin the block that includes the block header. In an exemplary embodiment,the data reference value may be a hash value generated via the hashingof the one or more data values. For instance, the block reference valuemay be the root of a Merkle tree generated using the one or more datavalues.

The use of the block reference value and data reference value in eachblock header may result in the blockchain being immutable. Any attemptedmodification to a data value would require the generation of a new datareference value for that block, which would thereby require thesubsequent block's block reference value to be newly generated, furtherrequiring the generation of a new block reference value in everysubsequent block. This would have to be performed and updated in everysingle node in the blockchain network 114 prior to the generation andaddition of a new block to the blockchain in order for the change to bemade permanent. Computational and communication limitations may makesuch a modification exceedingly difficult, if not impossible, thusrendering the blockchain immutable.

Each data value stored in the blockchain may correspond to anauthorization request received for a payment transaction. In some cases,there may be a separate blockchain for each consumer 104, where everydata value included in that blockchain may be related to an attemptedpayment transaction involving that consumer. In other cases, ablockchain may store data values for multiple consumers 104. In suchcases, each data value may include the account identifier, biographicalinformation, or other value used to identify the consumer 104 and/orprofile related therewith. Each data value may include the authorizationrequest or any data included therein that may be used in performing thefunctions discussed herein. In some embodiments, the processing server102 may submit any received authorization requests to a node in theblockchain network 114 for inclusion in the blockchain. In otherembodiments, an issuing institution 106 may, when an authorizationrequest is received, submit that authorization request to a node in theblockchain network 114. In yet other embodiments, merchant systems 110or the payment network 112 may be configured to provide authorizationrequests to nodes in the blockchain network 114 for inclusion on theblockchain during initial processing of the payment transaction. In someembodiments, the blockchain may be a private blockchain such that onlythe processing server 102 is capable of reading information added to theblockchain, such as to prevent one issuing institution 106 a from seeingpayment transactions involving a second issuing institution 106 b.

The methods and systems discussed herein enable a processing server 102to process payment transactions on behalf of multiple issuinginstitutions 106 that each involve a single consumer 104. The use ofauthorization requests from multiple issuing institutions 106 mayprovide for a more accurate fraud determination, which may result ingreater security for both consumers 104 and issuing institutions 106.The actions being performed by the processing server 102 separate fromthe issuing institutions 106 ensures that issuing institutions 106 donot need to update their existing systems or risk security or privacy bystoring transaction data for other issuing institutions 106. Inaddition, by the processing server 102 declining fraud-likely paymenttransactions on behalf of issuing institutions 106, issuing institutions106 may see less transaction messages, which may decrease networkbandwidth and processing power used, thus increasing operatingefficiency.

Processing Server

FIG. 2 illustrates an embodiment of a processing server 102 in thesystem 100. It will be apparent to persons having skill in the relevantart that the embodiment of the processing server 102 illustrated in FIG.2 is provided as illustration only and may not be exhaustive to allpossible configurations of the processing server 102 suitable forperforming the functions as discussed herein. For example, the computersystem 500 illustrated in FIG. 5 and discussed in more detail below maybe a suitable configuration of the processing server 102.

The processing server 102 may include a receiving device 202. Thereceiving device 202 may be configured to receive data over one or morenetworks via one or more network protocols. In some instances, thereceiving device 202 may be configured to receive data from issuinginstitutions 106, merchant systems 110, payment networks 112, blockchainnetworks 114, and other systems and entities via one or morecommunication methods, such as radio frequency, local area networks,wireless area networks, cellular communication networks, Bluetooth, theInternet, etc. In some embodiments, the receiving device 202 may becomprised of multiple devices, such as different receiving devices forreceiving data over different networks, such as a first receiving devicefor receiving data over a local area network and a second receivingdevice for receiving data via the Internet. The receiving device 202 mayreceive electronically transmitted data signals, where data may besuperimposed or otherwise encoded on the data signal and decoded,parsed, read, or otherwise obtained via receipt of the data signal bythe receiving device 202. In some instances, the receiving device 202may include a parsing module for parsing the received data signal toobtain the data superimposed thereon. For example, the receiving device202 may include a parser program configured to receive and transform thereceived data signal into usable input for the functions performed bythe processing device to carry out the methods and systems describedherein.

The receiving device 202 may be configured to receive data signalselectronically transmitted by issuing institutions 106 that aresuperimposed or otherwise encoded with account identifiers andbiographical information for transaction accounts issued thereby. Thereceiving device 202 may also be configured to receive data signalssuperimposed or otherwise encoded with authorization requests that maybe electronically transmitted by issuing institutions 106 or paymentnetworks 112. In some embodiments, the receiving device 202 may beconfigured to receive data signals electronically transmitted by issuinginstitutions 106 that are superimposed or otherwise encoded withauthorization responses for forwarding to payment networks 112. Inembodiments where blockchain is used, the receiving device 202 may beconfigured to receive data signals electronically transmitted by nodesin the blockchain network 114 that are superimposed or otherwise encodedwith new blocks and/or data values included therein.

The processing server 102 may also include a communication module 204.The communication module 204 may be configured to transmit data betweenmodules, engines, databases, memories, and other components of theprocessing server 102 for use in performing the functions discussedherein. The communication module 204 may be comprised of one or morecommunication types and utilize various communication methods forcommunications within a computing device. For example, the communicationmodule 204 may be comprised of a bus, contact pin connectors, wires,etc. In some embodiments, the communication module 204 may also beconfigured to communicate between internal components of the processingserver 102 and external components of the processing server 102, such asexternally connected databases, display devices, input devices, etc. Theprocessing server 102 may also include a processing device. Theprocessing device may be configured to perform the functions of theprocessing server 102 discussed herein as will be apparent to personshaving skill in the relevant art. In some embodiments, the processingdevice may include and/or be comprised of a plurality of engines and/ormodules specially configured to perform one or more functions of theprocessing device, such as a querying module 218, determination module220, transaction processing module 222, etc. As used herein, the term“module” may be software or hardware particularly programmed to receivean input, perform one or more processes using the input, and provides anoutput. The input, output, and processes performed by various moduleswill be apparent to one skilled in the art based upon the presentdisclosure.

The processing server 102 may include an account database 206. Theaccount database 206 may be configured to store a plurality of accountprofiles 208 using a suitable data storage format and schema. Theaccount database 206 may be a relational database that utilizesstructured query language for the storage, identification, modifying,updating, accessing, etc. of structured data sets stored therein. Eachaccount profile 208 may be a structured data set configured to storedata related to a consumer 104. Each account profile 208 may include atleast a plurality of primary account numbers or other accountidentifiers, where each is related to a transaction account issued tothe related consumer 104 or where the related consumer 104 is anauthorized user thereof. Each account profile 208 may also includebiographical information used to identify matching transaction accounts,as well as transaction data and/or authorization requests for pastpayment transactions, if applicable.

The processing server 102 may include a querying module 218. Thequerying module 218 may be configured to execute queries on databases toidentify information. The querying module 218 may receive one or moredata values or query strings, and may execute a query string basedthereon on an indicated database, such as the account database 206, toidentify information stored therein. The querying module 218 may thenoutput the identified information to an appropriate engine or module ofthe processing server 102 as necessary. The querying module 218 may, forexample, execute a query on the account database 206 to identify anaccount profile 208 related to a consumer 104 involved in an attemptedpayment transaction to identify recent authorization requests relatedthereto for use in determining likelihood of fraud for the attemptedpayment transaction.

The processing server 102 may also include a determination module 220.The determination module 220 may be configured to make determinationsfor the processing server 102 for use in performing the functionsdiscussed herein. The determination module 220 may receive instructionsas input, may make a determination based on the instructions, and mayoutput the determination to one or more modules of the processing server102. In some cases, the input may include data and/or rules to be usedin the determination. In other cases, the determination module 220 maybe configured to identify such data based on the instructions. Forexample, the determination module 220 may be configured to determinelikelihood of fraud for an attempted payment transaction based on thedata included in an authorization request received for the attemptedpayment transaction as well as data included in authorization requestsfor past payment transactions involving the same consumer 104 acrossmultiple issuing institutions 106. For instance, the determinationmodule 220 may compare times and geographic locations across theauthorization requests to determine likelihood of fraud. Thedetermination module 220 may also be configured to determine if anattempted payment transaction should be declined or forwarded to anassociated issuing institution 106 based on the determined likelihood offraud and a threshold value, such as may be associated with theassociated issuing institution 106.

In some embodiments, the processing server 102 may also include atransaction processing module 222. The transaction processing module 222may be configured to perform functions related to the processing ofelectronic payment transactions. For instance, the transactionprocessing module 222 may be configured generate authorizationresponses, forward authorization requests and responses, perform valueadded services, or any other functions associated with the routing andprocessing of electronic payment transactions.

The processing server 102 may also include a transmitting device 224.The transmitting device 224 may be configured to transmit data over oneor more networks via one or more network protocols. In some instances,the transmitting device 224 may be configured to transmit data toissuing institutions 106, merchant systems 110, payment networks 112,blockchain networks 114, and other entities via one or morecommunication methods, local area networks, wireless area networks,cellular communication, Bluetooth, radio frequency, the Internet, etc.In some embodiments, the transmitting device 224 may be comprised ofmultiple devices, such as different transmitting devices fortransmitting data over different networks, such as a first transmittingdevice for transmitting data over a local area network and a secondtransmitting device for transmitting data via the Internet. Thetransmitting device 224 may electronically transmit data signals thathave data superimposed that may be parsed by a receiving computingdevice. In some instances, the transmitting device 224 may include oneor more modules for superimposing, encoding, or otherwise formattingdata into data signals suitable for transmission.

The transmitting device 224 may be configured to electronically transmitdata signals to issuing institutions 106 that are superimposed orotherwise encoded with authorization requests and/or determinations oflikelihood of fraud for attempted payment transactions, as well as datasignals superimposed or otherwise encoded with requests for biographicalinformation. The transmitting device 224 may also be configured toelectronically transmit data signals to payment networks 112 or merchantsystems 110 that are superimposed or otherwise encoded withauthorization responses for attempted payment transactions. In someembodiments, the transmitting device 224 may be configured toelectronically transmit data signals to nodes in a blockchain network114 that are superimposed or otherwise encoded with authorizationrequest data for inclusion in a new blockchain data value or requestsfor blockchain data values.

The processing server 102 may also include a memory 210. The memory 210may be configured to store data for use by the processing server 102 inperforming the functions discussed herein, such as public and privatekeys, symmetric keys, etc. The memory 210 may be configured to storedata using suitable data formatting methods and schema and may be anysuitable type of memory, such as read-only memory, random access memory,etc. The memory 210 may include, for example, encryption keys andalgorithms, communication protocols and standards, data formattingstandards and protocols, program code for modules and applicationprograms of the processing device, and other data that may be suitablefor use by the processing server 102 in the performance of the functionsdisclosed herein as will be apparent to persons having skill in therelevant art. In some embodiments, the memory 210 may be comprised of ormay otherwise include a relational database that utilizes structuredquery language for the storage, identification, modifying, updating,accessing, etc. of structured data sets stored therein. The memory 210may be configured to store, for example, fraud determination rules,transaction routing data, transaction message formatting standard data,etc.

Process for Processing an Electronic Payment Transaction

FIG. 3 illustrates an example process 300 executed by the processingserver 102 in the system 100 for processing an electronic paymenttransaction on behalf of an issuing institution 106 based on alikelihood of fraud determined using past authorization requests frommultiple issuing institutions 106.

In step 302, the receiving device 202 of the processing server 102 mayreceive an authorization request for an attempted payment transaction,such as may be electronically transmitted by the payment network 112 oran issuing institution 106. The authorization request may be formattedaccording to one or more standards governing the interchange offinancial transaction messages and include a plurality of data elementsincluding data elements configured to store a primary account number,transaction time, and geographic location. In step 304, the processingserver 102 may determine if other transaction accounts are known thatare issued to the same consumer 104 involved in the payment transaction.Such a determination may be made by executing, by the querying module218 of the processing server 102, a query on the account database 206 ofthe processing server 102 to identify an account profile 208 thatincludes the primary account number included in the receivedauthorization request, and identifying if any other primary accountnumbers are included in that account profile 208, which may correspondto other transaction accounts including transaction accounts issued byother issuing institutions 106.

If the determination is that there are no other known transactionaccounts for the consumer 104, then, in step 306, the transactionprocessing module 222 may proceed to process the payment transactionusing traditional methods. In such cases, the processing server 102 maycontinue to make a fraud determination based on the one transactionaccount, or may forward the authorization request on to the issuinginstitution 106 for processing. If the determination is that othertransaction accounts are known, then, in step 308, the processing server102 may identify recent payment transactions conducted or attemptedusing the same and other transaction accounts. In some cases, the recentpayment transactions may be identified in the account profile 208. Inother cases, recent payment transactions may be identified in atransaction database in the processing server 102 used to storetransaction data. In yet other cases, the transactions may be identifiedas data values in a blockchain.

In step 310, the determination module 220 of the processing server 102may determine a likelihood of fraud for the attempted paymenttransaction based on data included in the received authorization requestas compared to transaction data in the identified related transactions.In an exemplary embodiment, the determination may be based on at least acomparison of the time and geographic location of the attempted paymenttransaction with the times and locations of the other recent paymenttransactions involving the consumer 104. In step 312, the determinationmodule 220 of the processing server 102 may determine if the likelihoodof fraud is above a threshold value set by the issuing institution 106that issued the transaction account used in the attempted paymenttransaction.

If the likelihood of fraud is below the threshold, then, in step 314,the payment transaction may be processed using traditional methods. Insuch an instance, the transmitting device 224 of the processing server102 may forward the authorization request to the associating issuinginstitution 106 for approval or denial. In some cases, the issuinginstitution 106 may return an authorization response to the processingserver 102, which may be received by the receiving device 202 thereof,for forwarding on to the payment network 112 using payment railsassociated therewith. If the likelihood of fraud for the attemptedpayment transaction is above the threshold, then, in step 316, theprocessing server 102 may decline the payment transaction. The declinemay be accomplished by the transaction processing module 222 of theprocessing server 102 generating an authorization response that includesa data element that stores a response code indicating denial of thepayment transaction, which is then electronically transmitted to thepayment network 112 by the transmitting device 224 of the processingserver 102 using payment rails associated therewith.

Exemplary Method for Processing an Electronic Payment Transaction

FIG. 4 illustrates a method 400 for the processing of an electronicpayment transaction by a processing server on behalf of an issuinginstitution based on a determined likelihood of fraud based on pastauthorization requests involving other issuing institutions.

In step 402, an account profile (e.g., an account profile 208) may bestored in an account database (e.g., the account database 206) of aprocessing server (e.g., the processing server 102), wherein the accountprofile includes at least a plurality of primary account numbers and oneor more biographical data values, where each of the plurality of primaryaccount numbers is associated with a transaction account and the one ormore biographical data values are associated with each of thetransaction accounts related to the plurality of primary accountnumbers. In step 404, a first authorization request for a first paymenttransaction may be received by a receiving device (e.g., the receivingdevice 202) of the processing server, wherein the first authorizationrequest is formatted according to one or more standards and includes aplurality of data elements configured to store transaction dataincluding at least a first primary account number of the plurality ofprimary account numbers, a first transaction time, and a firstgeographic location.

In step 406, the first payment transaction may be processed by theprocessing server (e.g., by the transaction processing module 222thereof). In step 408, a second authorization for a second paymenttransaction may be received by the receiving device of the processingserver from an external system (e.g., the payment network 112), whereinthe second authorization request is formatted according to the one ormore standards and includes a plurality of data elements configured tostore transaction data including at least a second primary accountnumber of the plurality of primary account numbers, a second transactiontime, and a second geographic location, where the second primary accountnumber is associated with a transaction account issued by a differentissuer than a transaction account associated with the first primaryaccount number.

In step 410, a likelihood of fraud may be determined by the processingserver (e.g., by the determination module 220 thereof) based on at leastthe first transaction time and first geographic location stored in thefirst authorization request and the second transaction time and secondgeographic location stored in the second authorization request. If thedetermined likelihood of fraud is below a predetermined threshold, then,in step 412, the second authorization request may be electronicallytransmitted to the different issuer by a transmitting device (e.g., thetransmitting device 224) of the processing server. If the determinedlikelihood of fraud is above the predetermined threshold, then, in step414, an authorization response for the second payment transactionindicating decline of the second payment transaction may beelectronically transmitted, by the transmitting device of the processingserver, to the external system.

In one embodiment, the method 400 may further include storing, in amemory (e.g., the memory 210) of the processing server, a blockchain,wherein the blockchain includes a plurality of blocks, each blockincluding at least a block header and one or more transaction datavalues, wherein the first authorization request is stored in a new blockadded to the blockchain as a new transaction data value included in thenew block prior to receiving the second authorization request. In afurther embodiment, the account profile may further include a uniqueidentifier and the new transaction data value may further include theunique identifier. In an even further embodiment, the unique identifiermay be a private key of a key pair and the unique identifier may beincluded in the new transaction data value as a digital signaturegenerated using the private key.

In some embodiments, the first primary account number may include anidentification number associated with a first issuing institution (e.g.,the issuing institution 106 a), and the second primary account numbermay include an identification number associated with a second issuinginstitution (e.g., the issuing institution 106 b) different from thefirst issuing institution. In one embodiment, the determination of alikelihood of fraud based on at least the first transaction time andfirst geographic location stored in the first authorization request andthe second transaction time and second geographic location stored in thesecond authorization request may be further based on an estimated traveltime between the first geographic location and the second geographiclocation compared to a difference in time between the first transactiontime and the second transaction time.

In some embodiments, the authorization response may be formattedaccording to the one or more standards. In a further embodiment, theauthorization response may include a plurality of data elementsincluding a data element configured to store a response code indicatingdecline of the payment transaction due to likelihood of fraud.

Computer System Architecture

FIG. 5 illustrates a computer system 500 in which embodiments of thepresent disclosure, or portions thereof, may be implemented ascomputer-readable code. For example, the processing server 102 of FIG. 1may be implemented in the computer system 500 using hardware, software,firmware, non-transitory computer readable media having instructionsstored thereon, or a combination thereof and may be implemented in oneor more computer systems or other processing systems. Hardware,software, or any combination thereof may embody modules and componentsused to implement the methods of FIGS. 3 and 4.

If programmable logic is used, such logic may execute on a commerciallyavailable processing platform configured by executable software code tobecome a specific purpose computer or a special purpose device (e.g.,programmable logic array, application-specific integrated circuit,etc.). A person having ordinary skill in the art may appreciate thatembodiments of the disclosed subject matter can be practiced withvarious computer system configurations, including multi-coremultiprocessor systems, minicomputers, mainframe computers, computerslinked or clustered with distributed functions, as well as pervasive orminiature computers that may be embedded into virtually any device. Forinstance, at least one processor device and a memory may be used toimplement the above described embodiments.

A processor unit or device as discussed herein may be a singleprocessor, a plurality of processors, or combinations thereof. Processordevices may have one or more processor “cores.” The terms “computerprogram medium,” “non-transitory computer readable medium,” and“computer usable medium” as discussed herein are used to generally referto tangible media such as a removable storage unit 518, a removablestorage unit 522, and a hard disk installed in hard disk drive 512.

Various embodiments of the present disclosure are described in terms ofthis example computer system 500. After reading this description, itwill become apparent to a person skilled in the relevant art how toimplement the present disclosure using other computer systems and/orcomputer architectures. Although operations may be described as asequential process, some of the operations may in fact be performed inparallel, concurrently, and/or in a distributed environment, and withprogram code stored locally or remotely for access by single ormulti-processor machines. In addition, in some embodiments the order ofoperations may be rearranged without departing from the spirit of thedisclosed subject matter.

Processor device 504 may be a special purpose or a general purposeprocessor device specifically configured to perform the functionsdiscussed herein. The processor device 504 may be connected to acommunications infrastructure 506, such as a bus, message queue,network, multi-core message-passing scheme, etc. The network may be anynetwork suitable for performing the functions as disclosed herein andmay include a local area network (LAN), a wide area network (WAN), awireless network (e.g., WiFi), a mobile communication network, asatellite network, the Internet, fiber optic, coaxial cable, infrared,radio frequency (RF), or any combination thereof. Other suitable networktypes and configurations will be apparent to persons having skill in therelevant art. The computer system 500 may also include a main memory 508(e.g., random access memory, read-only memory, etc.), and may alsoinclude a secondary memory 510. The secondary memory 510 may include thehard disk drive 512 and a removable storage drive 514, such as a floppydisk drive, a magnetic tape drive, an optical disk drive, a flashmemory, etc.

The removable storage drive 514 may read from and/or write to theremovable storage unit 518 in a well-known manner. The removable storageunit 518 may include a removable storage media that may be read by andwritten to by the removable storage drive 514. For example, if theremovable storage drive 514 is a floppy disk drive or universal serialbus port, the removable storage unit 518 may be a floppy disk orportable flash drive, respectively. In one embodiment, the removablestorage unit 518 may be non-transitory computer readable recordingmedia.

In some embodiments, the secondary memory 510 may include alternativemeans for allowing computer programs or other instructions to be loadedinto the computer system 500, for example, the removable storage unit522 and an interface 520. Examples of such means may include a programcartridge and cartridge interface (e.g., as found in video gamesystems), a removable memory chip (e.g., EEPROM, PROM, etc.) andassociated socket, and other removable storage units 522 and interfaces520 as will be apparent to persons having skill in the relevant art.

Data stored in the computer system 500 (e.g., in the main memory 508and/or the secondary memory 510) may be stored on any type of suitablecomputer readable media, such as optical storage (e.g., a compact disc,digital versatile disc, Blu-ray disc, etc.) or magnetic tape storage(e.g., a hard disk drive). The data may be configured in any type ofsuitable database configuration, such as a relational database, astructured query language (SQL) database, a distributed database, anobject database, etc. Suitable configurations and storage types will beapparent to persons having skill in the relevant art.

The computer system 500 may also include a communications interface 524.The communications interface 524 may be configured to allow software anddata to be transferred between the computer system 500 and externaldevices. Exemplary communications interfaces 524 may include a modem, anetwork interface (e.g., an Ethernet card), a communications port, aPCMCIA slot and card, etc. Software and data transferred via thecommunications interface 524 may be in the form of signals, which may beelectronic, electromagnetic, optical, or other signals as will beapparent to persons having skill in the relevant art. The signals maytravel via a communications path 526, which may be configured to carrythe signals and may be implemented using wire, cable, fiber optics, aphone line, a cellular phone link, a radio frequency link, etc.

The computer system 500 may further include a display interface 502. Thedisplay interface 502 may be configured to allow data to be transferredbetween the computer system 500 and external display 530. Exemplarydisplay interfaces 502 may include high-definition multimedia interface(HDMI), digital visual interface (DVI), video graphics array (VGA), etc.The display 530 may be any suitable type of display for displaying datatransmitted via the display interface 502 of the computer system 500,including a cathode ray tube (CRT) display, liquid crystal display(LCD), light-emitting diode (LED) display, capacitive touch display,thin-film transistor (TFT) display, etc.

Computer program medium and computer usable medium may refer tomemories, such as the main memory 508 and secondary memory 510, whichmay be memory semiconductors (e.g., DRAMs, etc.). These computer programproducts may be means for providing software to the computer system 500.Computer programs (e.g., computer control logic) may be stored in themain memory 508 and/or the secondary memory 510. Computer programs mayalso be received via the communications interface 524. Such computerprograms, when executed, may enable computer system 500 to implement thepresent methods as discussed herein. In particular, the computerprograms, when executed, may enable processor device 504 to implementthe methods illustrated by FIGS. 3 and 4, as discussed herein.Accordingly, such computer programs may represent controllers of thecomputer system 500. Where the present disclosure is implemented usingsoftware, the software may be stored in a computer program product andloaded into the computer system 500 using the removable storage drive514, interface 520, and hard disk drive 512, or communications interface524.

The processor device 504 may comprise one or more modules or enginesconfigured to perform the functions of the computer system 500. Each ofthe modules or engines may be implemented using hardware and, in someinstances, may also utilize software, such as corresponding to programcode and/or programs stored in the main memory 508 or secondary memory510. In such instances, program code may be compiled by the processordevice 504 (e.g., by a compiling module or engine) prior to execution bythe hardware of the computer system 500. For example, the program codemay be source code written in a programming language that is translatedinto a lower level language, such as assembly language or machine code,for execution by the processor device 504 and/or any additional hardwarecomponents of the computer system 500. The process of compiling mayinclude the use of lexical analysis, preprocessing, parsing, semanticanalysis, syntax-directed translation, code generation, codeoptimization, and any other techniques that may be suitable fortranslation of program code into a lower level language suitable forcontrolling the computer system 500 to perform the functions disclosedherein. It will be apparent to persons having skill in the relevant artthat such processes result in the computer system 500 being a speciallyconfigured computer system 500 uniquely programmed to perform thefunctions discussed above.

Techniques consistent with the present disclosure provide, among otherfeatures, systems and methods for processing electronic paymenttransactions. While various exemplary embodiments of the disclosedsystem and method have been described above it should be understood thatthey have been presented for purposes of example only, not limitations.It is not exhaustive and does not limit the disclosure to the preciseform disclosed. Modifications and variations are possible in light ofthe above teachings or may be acquired from practicing of thedisclosure, without departing from the breadth or scope.

What is claimed is:
 1. A method for processing an electronic paymenttransaction, comprising: storing, in a database of a processing server,an account profile, wherein the account profile includes at least aplurality of primary account numbers, where each of the plurality ofprimary account numbers is associated with a transaction account;receiving, by a processing server, a first authorization request for afirst payment transaction, wherein the first authorization requestincludes at least a first primary account number of the plurality ofprimary account numbers, a first transaction time, and a firstgeographic location; processing, by the processing server, the firstpayment transaction; receiving, by the processing server, a secondauthorization request for a second payment transaction, wherein thesecond authorization request includes at least a second primary accountnumber of the plurality of primary account numbers, a second transactiontime, and a second geographic location, where the second primary accountnumber is associated with a transaction account issued by a differentissuer than a transaction account associated with the first primaryaccount number; determining, by the processing server, a likelihood offraud based on at least the first transaction time and first geographiclocation stored in the first authorization request and the secondtransaction time and second geographic location stored in the secondauthorization request; and transmitting, by the processing server, anauthorization response for the second payment transaction to theexternal system indicating decline of the second payment transaction,prior to the completion of the second payment transaction, if thedetermined likelihood of fraud is above the predetermined threshold. 2.The method of claim 1, further comprising: storing, in a memory of theprocessing server, a blockchain, wherein the blockchain includes aplurality of blocks, each block including at least a block header andone or more transaction data values, wherein the first authorizationrequest is stored in a new block added to the blockchain as a newtransaction data value included in the new block prior to receiving thesecond authorization request.
 3. The method of claim 2, wherein theaccount profile further includes a unique identifier, and the newtransaction data value further includes the unique identifier.
 4. Themethod of claim 3, wherein the unique identifier is a private key of akey pair, and the unique identifier is included in the new transactiondata value as a digital signature generated using the private key. 5.The method of claim 1, wherein the first primary account number includesan identification number associated with a first issuing institution,and the second primary account number includes an identification numberassociated with a second issuing institution different from the firstissuing institution.
 6. The method of claim 1, wherein the determinationof a likelihood of fraud based on at least the first transaction timeand first geographic location stored in the first authorization requestand the second transaction time and second geographic location stored inthe second authorization request is further based on an estimated traveltime between the first geographic location and the second geographiclocation compared to a difference in time between the first transactiontime and the second transaction time.
 7. The method of claim 1, furthercomprising forwarding, by a transmitting device of the processingserver, the second authorization request to the different issuer if thedetermined likelihood of fraud is below a predetermined threshold. 8.The method of claim 1, wherein the authorization response includes aplurality of data elements including a data element configured to storea response code indicating decline of the payment transaction due tolikelihood of fraud.
 9. A system for processing an electronic paymenttransaction, comprising: a database of a processing server configured tostore an account profile, wherein the account profile includes at leasta plurality of primary account numbers, where each of the plurality ofprimary account numbers is associated with a transaction account; theprocessing server configured to receive a first authorization requestfor a first payment transaction, wherein the first authorization requestincludes at least a first primary account number of the plurality ofprimary account numbers, a first transaction time, and a firstgeographic location; the processing server configured to process thefirst payment transaction, the processing server is further configuredto receive a second authorization request for a second paymenttransaction, wherein the second authorization request includes at leasta second primary account number of the plurality of primary accountnumbers, a second transaction time, and a second geographic location,where the second primary account number is associated with a transactionaccount issued by a different issuer than a transaction accountassociated with the first primary account number, the processing serveris further configured to determine a likelihood of fraud based on atleast the first transaction time and first geographic location stored inthe first authorization request and the second transaction time andsecond geographic location stored in the second authorization request,and the transmitting device of the processing server is configured totransmit an authorization response for the second payment transaction tothe external system indicating decline of the second paymenttransaction, prior to the completion of the second payment transaction,if the determined likelihood of fraud is above the predeterminedthreshold.
 10. The system of claim 9, further comprising: a memory ofthe processing server configured to store a blockchain, wherein theblockchain includes a plurality of blocks, each block including at leasta block header and one or more transaction data values, wherein thefirst authorization request is stored in a new block added to theblockchain as a new transaction data value included in the new blockprior to receiving the second authorization request.
 11. The system ofclaim 10, wherein the account profile further includes a uniqueidentifier, and the new transaction data value further includes theunique identifier.
 12. The system of claim 11, wherein the uniqueidentifier is a private key of a key pair, and the unique identifier isincluded in the new transaction data value as a digital signaturegenerated using the private key.
 13. The system of claim 9, wherein thefirst primary account number includes an identification numberassociated with a first issuing institution, and the second primaryaccount number includes an identification number associated with asecond issuing institution different from the first issuing institution.14. The system of claim 9, wherein the determination of a likelihood offraud based on at least the first transaction time and first geographiclocation stored in the first authorization request and the secondtransaction time and second geographic location stored in the secondauthorization request is further based on an estimated travel timebetween the first geographic location and the second geographic locationcompared to a difference in time between the first transaction time andthe second transaction time.
 15. The system of claim 9, wherein thetransmitting device of the processing server is further configured totransmit the second authorization request to the different issuer if thedetermined likelihood of fraud is below a predetermined threshold. 16.The system of claim 9, wherein the authorization response includes aplurality of data elements including a data element configured to storea response code indicating decline of the payment transaction due tolikelihood of fraud.